home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / u_man / cat1 / srchtxt.z / srchtxt
Text File  |  1998-10-20  |  14KB  |  198 lines
  1.  
  2.  
  3.  
  4. ssssrrrrcccchhhhttttxxxxtttt((((1111))))                                                          ssssrrrrcccchhhhttttxxxxtttt((((1111))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _ssss_rrrr_cccc_hhhh_tttt_xxxx_tttt - display contents of, or search for a text string in, message
  10.      databases
  11.  
  12. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  13.      _ssss_rrrr_cccc_hhhh_tttt_xxxx_tttt [_----_ssss] [_----_iiii _m_s_g_n_u_m] [_----_llll _l_o_c_a_l_e] [_----_mmmm _m_s_g_f_i_l_e_,,,, ...]  [_t_e_x_t]
  14.  
  15. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  16.      The _ssss_rrrr_cccc_hhhh_tttt_xxxx_tttt utility is used to display all the text strings in message
  17.      databases, or to search for a text string in message databases [see
  18.      _mmmm_kkkk_mmmm_ssss_gggg_ssss(1)].  These databases are files in the directory
  19.      _////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_l_o_c_a_l_e_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS [see _ssss_eeee_tttt_llll_oooo_cccc_aaaa_llll_eeee(3C)], unless a file
  20.      name given with the _----_mmmm option contains a _////.  The directory _l_o_c_a_l_e can be
  21.      viewed as the name of the language in which the text strings are written.
  22.      When the _----_llll option is not used, the _l_o_c_a_l_e directory searched is
  23.      specified by the _LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS environment variable if it is set to a non-
  24.      empty value.  Otherwise, it is specified by the environment variable _LLLL_AAAA_NNNN_GGGG
  25.      if it is set to a non-empty value.  Otherwise, the directory _CCCC is used.
  26.      Text strings may contain supplementary code set characters.
  27.  
  28.      If no _t_e_x_t argument is present, then all the text strings in the files
  29.      accessed will be displayed.
  30.  
  31.      The meanings of the options are as follows:
  32.  
  33.      _----_ssss          suppress printing of the message sequence numbers of the
  34.                  messages being displayed
  35.  
  36.      _----_llll _l_o_c_a_l_e   access files in the directory
  37.                  _////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_l_o_c_a_l_e_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS.  If _----_mmmm _m_s_g_f_i_l_e is also
  38.                  supplied, _l_o_c_a_l_e is ignored for _m_s_g_f_i_l_es containing a _////.
  39.  
  40.      _----_mmmm _m_s_g_f_i_l_e  access file(s) specified by one or more _m_s_g_f_i_l_es.  If _m_s_g_f_i_l_e
  41.                  contains a _//// character, then _m_s_g_f_i_l_e _i_s interpreted as a
  42.                  pathname; otherwise, it will be assumed to be in the
  43.                  directory determined as described above.  To specify more
  44.                  than one _m_s_g_f_i_l_e, separate the file names using commas.
  45.  
  46.      _----_iiii _m_s_g_n_u_m   display only the message whose numeric id equals _m_s_g_n_u_m.
  47.                  This option should not normally be used with a search text.
  48.  
  49.      _t_e_x_t        search for the text string specified by _t_e_x_t and display each
  50.                  one that matches.  _t_e_x_t can take the form of a regular
  51.                  expression [see _eeee_dddd(1)].
  52.  
  53.      If the _----_ssss option is not specified, the displayed text is prefixed by
  54.      message sequence numbers.  The message sequence numbers are enclosed in
  55.      angle brackets:  _<<<<_m_s_g_f_i_l_e_::::_m_s_g_n_u_m_>>>>_....
  56.  
  57.      _m_s_g_f_i_l_e     name of the file where the displayed text occurred
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. ssssrrrrcccchhhhttttxxxxtttt((((1111))))                                                          ssssrrrrcccchhhhttttxxxxtttt((((1111))))
  71.  
  72.  
  73.  
  74.      _m_s_g_n_u_m      sequence number in _m_s_g_f_i_l_e where the displayed text occurred
  75.  
  76.      This display is in the format used by _gggg_eeee_tttt_tttt_xxxx_tttt(1) and _gggg_eeee_tttt_tttt_xxxx_tttt(3C).
  77.  
  78. EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
  79.      The following examples show uses of _ssss_rrrr_cccc_hhhh_tttt_xxxx_tttt.
  80.  
  81.      Example 1:
  82.  
  83.           If message files have been installed in a locale named _ffff_rrrr_eeee_nnnn_cccc_hhhh by
  84.           using _mmmm_kkkk_mmmm_ssss_gggg_ssss(1), then you could display the entire set of text
  85.           strings in the _ffff_rrrr_eeee_nnnn_cccc_hhhh locale (_////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_ffff_rrrr_eeee_nnnn_cccc_hhhh_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS_////_****)
  86.           by entering:
  87.                _ssss_rrrr_cccc_hhhh_tttt_xxxx_tttt _----_llll _ffff_rrrr_eeee_nnnn_cccc_hhhh
  88.  
  89.      Example 2:
  90.  
  91.           If a set of error messages associated with the UNIX operating system
  92.           have been installed in the file _UUUU_XXXX in the _ffff_rrrr_eeee_nnnn_cccc_hhhh locale
  93.           (_////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_ffff_rrrr_eeee_nnnn_cccc_hhhh_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS_////_UUUU_XXXX), then, using the value of
  94.           the _LLLL_AAAA_NNNN_GGGG environment variable to determine the locale to be
  95.           searched, you could search that file in that locale for all error
  96.           messages dealing with files by entering:
  97.  
  98.                _LLLL_AAAA_NNNN_GGGG_====_ffff_rrrr_eeee_nnnn_cccc_hhhh_;;;; _eeee_xxxx_pppp_oooo_rrrr_tttt _LLLL_AAAA_NNNN_GGGG
  99.                _ssss_rrrr_cccc_hhhh_tttt_xxxx_tttt _----_mmmm _UUUU_XXXX _""""_[[[[_FFFF_ffff_]]]]_iiii_cccc_hhhh_iiii_eeee_rrrr_""""
  100.  
  101.           If _////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_ffff_rrrr_eeee_nnnn_cccc_hhhh_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS_////_UUUU_XXXX contained the following
  102.           strings:
  103.  
  104.                _EEEE_rrrr_rrrr_eeee_uuuu_rrrr _EEEE_////_SSSS_\\\\_nnnn
  105.                _LLLL_iiii_ssss_tttt_eeee _dddd_''''_aaaa_rrrr_gggg_uuuu_mmmm_eeee_nnnn_tttt_ssss _tttt_rrrr_oooo_pppp _llll_oooo_nnnn_gggg_uuuu_eeee_\\\\_nnnn
  106.                _FFFF_iiii_cccc_hhhh_iiii_eeee_rrrr _iiii_nnnn_eeee_xxxx_iiii_ssss_tttt_aaaa_nnnn_tttt_\\\\_nnnn
  107.                _AAAA_rrrr_gggg_uuuu_mmmm_eeee_nnnn_tttt _iiii_nnnn_vvvv_aaaa_llll_iiii_dddd_eeee_\\\\_nnnn
  108.                _TTTT_rrrr_oooo_pppp _dddd_eeee _ffff_iiii_cccc_hhhh_iiii_eeee_rrrr_ssss _oooo_uuuu_vvvv_eeee_rrrr_tttt_ssss_\\\\_nnnn
  109.                _FFFF_iiii_cccc_hhhh_iiii_eeee_rrrr _tttt_rrrr_oooo_pppp _llll_oooo_nnnn_gggg_\\\\_nnnn
  110.                _TTTT_rrrr_oooo_pppp _dddd_eeee _llll_iiii_eeee_nnnn_ssss_\\\\_nnnn
  111.                _AAAA_rrrr_gggg_uuuu_mmmm_eeee_nnnn_tttt _hhhh_oooo_rrrr_ssss _dddd_uuuu _dddd_oooo_mmmm_aaaa_iiii_nnnn_eeee_\\\\_nnnn
  112.                _IIII_dddd_eeee_nnnn_tttt_iiii_ffff_iiii_cccc_aaaa_tttt_eeee_uuuu_rrrr _ssss_uuuu_pppp_pppp_rrrr_iiii_mmmm_\\\\_nnnn
  113.                _EEEE_tttt_rrrr_eeee_iiii_nnnn_tttt_eeee _ffff_aaaa_tttt_aaaa_llll_eeee_\\\\_nnnn
  114.                  _....
  115.                  _....
  116.                  _....
  117.  
  118.           then the following strings would be displayed:
  119.                _<<<<_UUUU_XXXX_::::_3333_>>>>_FFFF_iiii_cccc_hhhh_iiii_eeee_rrrr _iiii_nnnn_eeee_xxxx_iiii_ssss_tttt_aaaa_nnnn_tttt_\\\\_nnnn
  120.                _<<<<_UUUU_XXXX_::::_5555_>>>>_TTTT_rrrr_oooo_pppp _dddd_eeee _ffff_iiii_cccc_hhhh_iiii_eeee_rrrr_ssss _oooo_uuuu_vvvv_eeee_rrrr_tttt_ssss_\\\\_nnnn
  121.                _<<<<_UUUU_XXXX_::::_6666_>>>>_FFFF_iiii_cccc_hhhh_iiii_eeee_rrrr _tttt_rrrr_oooo_pppp _llll_oooo_nnnn_gggg_\\\\_nnnn
  122.  
  123.  
  124.  
  126.  
  127.  
  128.                                                                         PPPPaaaaggggeeee 2222
  129.  
  130.  
  131.  
  132.  
  133.  
  134.  
  135. ssssrrrrcccchhhhttttxxxxtttt((((1111))))                                                          ssssrrrrcccchhhhttttxxxxtttt((((1111))))
  136.  
  137.  
  138.  
  139.      Example 3:
  140.  
  141.           If a set of error messages associated with the UNIX operating system
  142.           has been installed in the file _UUUU_XXXX and a set of error messages
  143.           associated with the INGRESS database product have been installed in
  144.           the file _iiii_nnnn_gggg_rrrr_eeee_ssss_ssss, both in the _gggg_eeee_rrrr_mmmm_aaaa_nnnn locale, then you could search
  145.           for the pattern _[[[[_DDDD_dddd_]]]]_aaaa_tttt_eeee_iiii in both the files _UUUU_XXXX and _iiii_nnnn_gggg_rrrr_eeee_ssss_ssss in the
  146.           _gggg_eeee_rrrr_mmmm_aaaa_nnnn locale by entering:
  147.  
  148.                _ssss_rrrr_cccc_hhhh_tttt_xxxx_tttt _----_llll _gggg_eeee_rrrr_mmmm_aaaa_nnnn _----_mmmm _UUUU_XXXX_,,,,_iiii_nnnn_gggg_rrrr_eeee_ssss_ssss _""""_[[[[_DDDD_dddd_]]]]_aaaa_tttt_eeee_iiii_""""
  149.  
  150. FFFFIIIILLLLEEEESSSS
  151.      _////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_CCCC_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS_////_****         default files created by
  152.                                              _mmmm_kkkk_mmmm_ssss_gggg_ssss(1)
  153.  
  154.      _////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_l_o_c_a_l_e_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS_////_****    message files created by
  155.                                              _mmmm_kkkk_mmmm_ssss_gggg_ssss(1)
  156.  
  157. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  158.      _eeee_dddd(1), _eeee_xxxx_ssss_tttt_rrrr(1), _gggg_eeee_tttt_tttt_xxxx_tttt(1), _mmmm_kkkk_mmmm_ssss_gggg_ssss(1), _gggg_eeee_tttt_tttt_xxxx_tttt(3C), _ssss_eeee_tttt_llll_oooo_cccc_aaaa_llll_eeee(3C),
  159.      _eeee_nnnn_vvvv_iiii_rrrr_oooo_nnnn(5)
  160.  
  161. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  162.      The error messages produced by _ssss_rrrr_cccc_hhhh_tttt_xxxx_tttt are intended to be self-
  163.      explanatory.  They indicate an error in the command line or errors
  164.      encountered while searching for a particular locale and/or message file.
  165.  
  166.  
  167.  
  168.  
  169.  
  170.  
  171.  
  172.  
  173.  
  174.  
  175.  
  176.  
  177.  
  178.  
  179.  
  180.  
  181.  
  182.  
  183.  
  184.  
  185.  
  186.  
  187.  
  188.  
  189.  
  190.  
  191.  
  192.  
  193.  
  194.                                                                         PPPPaaaaggggeeee 3333
  195.  
  196.  
  197.  
  198.